Apologies for the length of this document, and how it require re-reading every
time you update if you want to be absolutely certain to fixable avoid bugs.
Suggestions to fix this are welcome.
I think that reading upwards from the version from which you are updating
should be sufficient. Bear in mind that features change over time and that each
section is not accuruate to the current version.

You may wish to refer also to "About Boutique.txt", which contains a full change
list sorted clearly by version.

== 2.1 ==

The major feature of 2.1 is the cache system. If you designed some sort of web
application, bukkit plugin, etc that directly editted the Boutique table,
it will no longer function correctly, and results are unpredictable.
Boutique no longer performs a read of the database when using something like
'/shop go' or /shop list', it instead reads from the caches.
Applications/plugins/etc that simply read the database without altering it
will continue to function correctly.

== 2.0 ==

When you udpate to 2.0 and beyond, you will probably have to sort out the
permissions. You can find help on this in 'Setting Up Permissions.txt'.

There is another update to the config file. See below for more information.

There have been a few renames of MySQL stuff. 
 - Database table 'Shops' has been renamed to 'boutique_shops'
 - Fields have been renamed in the table:
    - 'Shop' is now 'owner'
    - 'Description' is now 'description'
    - 'Status' is now 'status'

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Please refer also to the 2.1 help regarding the following information      !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! If you have developed any applications/plugins that interact with the      !!
!! Boutique database, you should update it to take into account these name    !!
!! changes. In future, I may allow the table name to be configured.           !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Your old config file should be backed up automatically, and a new one created
with all your options passing over to the current one.
Changes in the config file upon version 2.0 -

- removed TP config - you now control who can teleport where and when with
    permissions (More flexible than catch-all rules for everyone)
- renamed colourListHeadShop to colourListTitleShop. (Better name, I think.)
- renamed colourListHeadDescription to colourListTitleDescription. (Better name, I think.)
- refactored colourlistEntryShop to four seperate values - you can now colour
   (online/offline)/(open/closed) shops differently. (This is helpful if some
   players only have perms to teleport to, for example, open shops.)

== 1.3 ==

None (actually, I just can't remember. I don't _think_ there was anything)

== 1.2 ==

Your old config file should be backed up automatically, and a new one created
with all your options passing over to the current one.
Changes in the config file from 1.1 to 1.2/1.3 -

The new config file is easier to read, and contains more options. You may wish
to refer to "Installation and config" for some details on these options. The
added options are:

- database_* options have been renamed to mysql_*
- You can now change the name of the database with the new option,
  "mysql_database"
- There are a set of options relating to what kind of shops can appear in the
  list of shops given by '/shop list'


